Skip to main content

This is a new service – your feedback will help us to improve it.

Peak District National Park Authority

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

Long Rake, Youlgrave

reference
TPO-005-W4
name
Long Rake, Youlgrave
tree-preservation-order

undefined

TPO-005-W4
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-1.734483 53.172112,-1.734443 53.172163,-1.734389 53.172254,-1.734230 53.172391,-1.733861 53.172425,-1.733219 53.172446,-1.732212 53.172489,-1.731254 53.172518,-1.730352 53.172554,-1.730187 53.172550,-1.730130 53.172540,-1.729690 53.172507,-1.729602 53.172494,-1.729422 53.172471,-1.728835 53.172367,-1.728179 53.172268,-1.727411 53.172161,-1.727267 53.172137,-1.727177 53.172118,-1.727112 53.172102,-1.727063 53.172086,-1.727048 53.172174,-1.726938 53.172766,-1.726609 53.172822,-1.726536 53.172840,-1.726264 53.172915,-1.726162 53.172945,-1.725594 53.173130,-1.725535 53.173147,-1.725114 53.173322,-1.724595 53.173582,-1.724402 53.173677,-1.724271 53.173736,-1.724343 53.173771,-1.723614 53.174053,-1.723389 53.174171,-1.723253 53.174101,-1.722963 53.174273,-1.722894 53.174292,-1.722612 53.174341,-1.722433 53.174379,-1.721986 53.174517,-1.720445 53.174808,-1.720116 53.174864,-1.719389 53.175017,-1.719286 53.175047,-1.718747 53.175162,-1.718187 53.175229,-1.717895 53.175267,-1.717797 53.175267,-1.717711 53.175270,-1.717615 53.175261,-1.717581 53.175248,-1.717561 53.175236,-1.717543 53.175218,-1.717543 53.175200,-1.717538 53.175172,-1.717544 53.175157,-1.717568 53.175142,-1.717600 53.175117,-1.717707 53.175026,-1.717438 53.174962,-1.717249 53.175082,-1.716977 53.175234,-1.716647 53.175423,-1.717488 53.175700,-1.717563 53.175710,-1.717637 53.175707,-1.717678 53.175701,-1.717889 53.175654,-1.718145 53.175593,-1.719302 53.175307,-1.719688 53.175215,-1.720264 53.175075,-1.720421 53.175038,-1.720611 53.174996,-1.720711 53.174965,-1.720721 53.174954,-1.720739 53.174946,-1.720850 53.174929,-1.720857 53.174937,-1.721135 53.174869,-1.721268 53.174832,-1.721270 53.174829,-1.721415 53.174801,-1.722240 53.174593,-1.722394 53.174562,-1.723098 53.174371,-1.723704 53.174204,-1.724529 53.173941,-1.724595 53.173918,-1.724631 53.173902,-1.724669 53.173880,-1.724676 53.173869,-1.724737 53.173839,-1.724751 53.173846,-1.724870 53.173804,-1.724957 53.173768,-1.725661 53.173442,-1.725937 53.173332,-1.726153 53.173256,-1.726245 53.173226,-1.726426 53.173173,-1.726443 53.173169,-1.726493 53.173165,-1.726559 53.173131,-1.726673 53.173093,-1.726888 53.173031,-1.726997 53.173005,-1.727069 53.172990,-1.727141 53.172977,-1.727292 53.172954,-1.727296 53.172959,-1.727308 53.172965,-1.727331 53.172971,-1.727345 53.172972,-1.727360 53.172967,-1.727384 53.172946,-1.727427 53.172958,-1.727451 53.172957,-1.727476 53.172952,-1.727494 53.172946,-1.727509 53.172938,-1.727515 53.172932,-1.728226 53.172874,-1.728530 53.172854,-1.729359 53.172860,-1.729500 53.172859,-1.729726 53.172852,-1.729737 53.172849,-1.729756 53.172833,-1.729817 53.172831,-1.729822 53.172848,-1.730322 53.172835,-1.730976 53.172807,-1.732201 53.172741,-1.733252 53.172688,-1.733273 53.172688,-1.733276 53.172700,-1.733334 53.172697,-1.733333 53.172680,-1.733382 53.172675,-1.733424 53.172686,-1.733471 53.172689,-1.734079 53.172663,-1.734083 53.172639,-1.734224 53.172629,-1.734244 53.172640,-1.734263 53.172640,-1.734278 53.172627,-1.735996 53.172536,-1.736011 53.172534,-1.736033 53.172534,-1.736041 53.172533,-1.736060 53.172527,-1.736071 53.172519,-1.736059 53.172507,-1.734483 53.172112)))
point
POINT (-1.726432 53.173448)
notes
entry-date
2026-07-22
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Peak District National Park Authority’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL